Enhanced peer-to-peer networking exchange

ABSTRACT

Systems, methods, and computer program products are disclosed for improving ease in transmitting information between peer devices. Communications devices establish a peer group. Each communications device in the group assigns different sections of its touchscreen to the other devices in the group. To transfer information to another device in the group, the user swipes on the touchscreen towards the assigned section for the target communications device. Upon detecting the swipe, and determining that the swipe was towards the assigned section, the communications device initiates a transfer of the information to the target communications device. This may involve confirmation at the device or a paired device before transfer, or no confirmation. Receipt of the information at the target communications device may trigger notifications to be displayed. It may also trigger a request for acceptance of the transfer at the target communications device after which receipt is confirmed.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims priority to and is a continuation of U.S.patent application Ser. No. 16/103,588, filed Aug. 14, 2018, whichclaims priority to and is a continuation of U.S. patent application Ser.No. 14/971,190, filed Dec. 16, 2015, all of which are incorporatedherein by reference in their entirety.

TECHNICAL FIELD

The present disclosure generally relates to communications betweencommunications devices, and more particularly to the contemporaneoustransfer of different types of information to other communicationsdevices based on one or more user gestures or actions.

BACKGROUND

Transferring information between devices typically involves entering anaddress for the targeted recipient, e.g., an address that some deviceassociated with the target recipient is able to access, followed byrequesting that the information be transferred. This may be true even ifthe target recipient, and a capable device, is within some smalldistance from the initiating device (e.g., a predetermined number offeet from each other). This lacks the convenience made available frompeer-to-peer communication technologies.

Devices that implement peer-to-peer technologies also are subject todrawbacks. Even when a peer connection is established, the user of theinitiating device must still typically identify by some form of addressthe target recipient. In other situations, the devices are onlyconfigured to enable the transfer of information when just two devicesare connected together via a network connection. This precludessituations, however, where there are multiple devices within an areathat desire to share information with the other devices. Thus, there isa need for techniques to improve the ability for multiple networkeddevices to transfer information amongst each other with greater ease.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a diagram of an exemplary communications environment accordingto embodiments of the present disclosure.

FIG. 2 is a block diagram of an exemplary mobile communications deviceaccording to embodiments of the present disclosure.

FIG. 3 is a block diagram of an exemplary mobile communications deviceaccording to embodiments of the present disclosure.

FIG. 4 is a diagram of an exemplary wireless communications environmentaccording to embodiments of the present disclosure.

FIG. 5 is a diagram of an exemplary wireless communications environmentaccording to embodiments of the present disclosure.

FIG. 6 is a diagram of an exemplary wireless communications environmentaccording to embodiments of the present disclosure.

FIG. 7 is a flow diagram illustrating an embodiment of a method forenhanced peer-to-peer networking exchanges according to an embodiment ofthe present disclosure.

FIG. 8 is a flow diagram illustrating an embodiment of a method forenhanced peer-to-peer networking exchanges according to an embodiment ofthe present disclosure.

FIG. 9 is a schematic view illustrating an embodiment of a computingsystem.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with theappended drawings, is intended as a description of variousconfigurations and is not intended to represent the only configurationsin which the concepts described herein may be practiced. The detaileddescription includes specific details for the purpose of providing athorough understanding of the various concepts. However, it will beapparent to those skilled in the art that these concepts may bepracticed without these specific details. In some instances, well-knownstructures and components are shown in block diagram form in order toavoid obscuring such concepts.

The present disclosure provides systems, methods, and computer programproducts for improving the ease with which information is transmittedbetween peer devices. According to embodiments of the presentdisclosure, multiple communications devices establish a peer groupamongst themselves, whether via direct communications or via anintermediary such as a network. Each communications device in the peergroup assigns different sections of its touchscreen to the otherdifferent devices in the peer group.

When the user of a communications device desires to transfer information(such as a monetary amount, an image, text, other data, etc.) to anotherof the communications devices in the peer group, the user swipes on thetouchscreen towards the assigned section of the touchscreen assigned tothe particular communications device. Upon detecting the swipe, anddetermining that the swipe was towards the assigned section, thecommunications device initiates a transfer of the information (e.g.,information entered into or arrived at on the touchscreen or determinedfrom the swipe itself, such as a number of fingers involved in theswipe) to the target communications device. In some embodiments, thismay involve confirmation at the communications device or a paired device(e.g., a smartwatch) before transfer, while in other embodiments, thetransfer may occur without further interruption.

Receipt of the transferred information at the target communicationsdevice may trigger one or more notifications to be displayed at thetarget communications device. It may also trigger the targetcommunications device to request acceptance of the transfer at thetarget communications device before the transfer can be complete. Thetarget communications device may then confirm receipt (or declinereceipt) of the information to the sending communications device.

Referring now to FIG. 1, an embodiment of an exemplary communicationsenvironment 100 is illustrated. The communications environment 100 mayinclude a number of mobile communications devices 102, one or morenetworks 108, and a global navigation satellite system (GNSS) 110. Thecommunications environment 100 illustrated in FIG. 1 is simplified forsake of illustration.

The communications environment 100 may support operation on multiplecarriers (e.g., waveform signals of different frequencies for wirelesscommunications, or wired communications). As an example, thecommunications environment 100 may be a multi-carrier LTE networkcapable of efficiently allocating network resources. The communicationsenvironment 100 is one example of a network to which various aspects ofthe disclosure apply.

The communications environment 100 includes one or more mobilecommunications devices 102, illustrated in FIG. 1 as mobilecommunications devices 102 a, 102 b, and 102 c. The mobilecommunications devices 102 a/102 b/102 c may be, for example, UserEquipment (UEs). The mobile communications devices 102 a/102 b/102 c mayeach also be referred to as a terminal, a mobile station, a subscriberunit, etc. A mobile communications device 102 may be a cellular phone, asmartphone, a personal digital assistant, a wireless modem, a laptopcomputer, a tablet computer, a tag (e.g., RFID tag), etc., to name justa few examples. The mobile communications devices 102 a/102 b/102 c maybe location-aware, for example by including circuitry and/or software toenable the mobile communications devices 102 a/102 b/102 c to determinetheir own locations.

For example, one or more of the mobile communications devices 102 a/102b/102 c may include circuitry and/or software that enable them to be incommunication with the GNSS 110 in order to determine location. The GNSS110 may be, for example, the Global Positioning System (GPS), Galileo,GLONASS, BeiDou, or some other such system that enables the mobilecommunications devices 102 a/102 b/102 c to determine geolocationinformation from signals provided by individual satellites of the GNSS110. The circuitry and/or software of mobile communications devices 102a/102 b/102 c may additionally or alternatively enable locationdetermination based on other parameters, such as base stationtriangulation, time of flight measurements, etc.

The mobile communications devices 102 a/102 b/102 c may communicate witheach other (as well as other devices) via one or more connections. Forexample, the mobile communications device 102 a may be capable ofestablishing a peer-to-peer (P2P) session 104 with one or both of themobile communications devices 102 b and 102 c. Similarly, the mobilecommunications device 102 b may be capable of establishing apeer-to-peer session 104 with one or both of the mobile communicationsdevices 102 a and 102 c. Similarly, the mobile communications device 102c may be capable of establishing a peer-to-peer session 104 with one orboth of the mobile communications devices 102 a and 102 b.

For example, the mobile communications devices 102 a/102 b/102 c may becapable of (e.g., includes one or more associated transceivers for)linking to each other via device-to-device (D2D) links, such that theP2P sessions 104 may constitute D2D links. As another example, themobile communications devices 102 a/102 b/102 c may be capable of (e.g.,includes one or more associated transceivers for) connecting viaBluetooth or near field communications (NFC) with each other, to namejust a few examples. The mobile communications devices 102 a/102 b/102 cmay all establish the same types of P2P sessions 104 with each other(e.g., all using the same linking technology/protocols), oralternatively may use a variety of technologies/protocols in order toestablish the P2P sessions 104 in the communications environment 100.

Alternatively, one or more of the mobile communications devices 102a/102 b/102 c may establish connections to each other via the network108. For example, the mobile communications device 102 a may establishthe connection 106 a with the network 108, the mobile communicationsdevices 102 b may establish the connection 106 b with the network 108,and the mobile communications device 102 c may establish the connection106 c with the network 108. For example, the mobile communicationsdevice 102 a may communicate with mobile communications device 102 b,via the network 108, by way of the connections 106 a and 106 b (e.g.,the connection 106 a constitutes an uplink to the network 108 and theconnection 106 b a downlink from the network 108). Similarly, the mobilecommunications device 102 may communicate with mobile communicationsdevice 102 c, via the network 108, by way of connections 106 a and 106c. Similar examples apply with respect to the other mobilecommunications devices 102 b and 102 c.

The network 108 may be, for example, a core network, an access network,other network, and/or any combination of networks. The network 108 mayinclude one or more base stations. For example, one or more the basestations may include an evolved Node B (eNodeB). A base station may alsobe referred to as a base transceiver station or an access point. Therecould be one to many base stations, as well as be an assortment ofdifferent types such as macro, pico, and/or femto base stations. Thebase stations may also communicate with one another directly orindirectly, such as via network 108. The network 108 may be an LTEnetwork or a WiFi network, to name just a few examples. The mobilecommunications devices 102 may use the network 108 to convey the datacommunications between them according to embodiments of the presentdisclosure. The mobile communications devices 102 may use one or moreelements of the network 108 to discover each other, while in otherembodiments the mobile communications devices 102 may discover eachother through NFC or Bluetooth ad-hoc connections for initial sessionnegotiation and continue communication via NFC or Bluetooth, oralternatively via network 108.

In another embodiment, an intermediary such as the network 108 mayfunction to initially assist different mobile communications devices 102to discover each other and/or establish peer-to-peer sessions 104 asillustrated in FIG. 1. For example, the mobile communications device 102a may send a message to the network 108, to which the mobilecommunications device 102 a is connected (e.g., a WiFi network),intended to reach the mobile communications device 102 b. The messagemay include a unique identifier or code that the mobile communicationsdevice 102 b may use to initiate the peer-to-peer session 104 betweenthe two mobile communications devices.

One of the mobile communications devices 102 may operate as a host toother mobile communications devices 102 in sending and receivinginformation according to embodiments of the present disclosure. Forexample, the mobile communications device 102 a in FIG. 1 may designateitself as a host of a group (ad-hoc or otherwise), or be designated byanother mobile communications device 102 or network 108 element as ahost. As host, the mobile communications device 102 a may provide aunique PIN/identifier or other code (e.g., a QR code) via email,messaging, image presentation, NFC, or other communication type to oneor more other mobile communications devices 102, such as mobilecommunications device 102 b.

As another example, a service provider may serve as host to a group ofdifferent mobile communications devices 102 (ad-hoc or otherwise)seeking to exchange information together according to embodiments of thepresent disclosure. The service provider (e.g., PayPal of San Jose,Calif. to name just one example) may be accessed by one or more mobilecommunications devices 102 via the network 108, for example. To ensuresecurity, the service provider may, in response to the request to hostthe ad-hoc group, provide a code for desired group members to enter tojoin the hosted group. Alternatively, the service provider may check theaddress information of each mobile communications device 102 desiring tojoin (e.g., IP address/subnet information, etc.) to confirm that themobile communications devices 102 are within a predetermined range ofeach other (e.g., a certain number of feet or yards/meters from eachother, such as a range that would be associated with remaining invisibility of each other). With this information, the different mobilecommunications devices 102 seeking to join the same group may then joinand proceed with exchanging information according to embodiments of thepresent disclosure (whether via direct P2P protocols or via someintermediary such as network 108).

Once various mobile communications devices 102 are connected in apeer-to-peer group, whether hosted, decentralized (no host), directlyconnected to each other or via an intermediary such as network 108, themobile communications devices 102 in the group may assign differentsections of their screens to the different mobile communications devices102 that are members of the group. For example, if the group consists ofthe mobile communications devices 102 a, 102 b, and 102 c of FIG. 1,each device may assign two sections of their respective display screensto represent targets for the two other mobile communications devices 102in the group. For example, mobile communications device 102 b may assignan upper left corner of its screen to represent the mobilecommunications device 102 a and an upper right corner of its screen torepresent the mobile communications device 102 c. This may be performedwhile in a specific application that has integrated embodiments of thepresent disclosure, or unrelated to any specific application (e.g.,while in a “home” screen of a graphical user interface (GUI) of themobile communications device 102 b).

Once sections of the screen are assigned, the mobile communicationsdevice 102 b is ready to transfer information to one or more of themobile communications devices 102 a/102 c in the group. For example, ifthe user of the mobile communications device 102 b desires to transfermoney to the mobile communications device 102 a, the user may identifyan amount of money to be sent and then swipe on the screen (which, inthis example, is a touchscreen) in the general direction toward theupper left corner of the screen. This indicates that the identifiedamount should be transferred to the mobile communications device 102 a.In response, a message is sent to the mobile communications device 102 afrom the mobile communications device 102 b via the connectionpreviously established for the group (for example, P2P session 104 oruplink 106 b/downlink 106 a). This may be accompanied by auditory and/orvisual indicators of the identified amount being sent (e.g., a swooshingsound and/or perspective graphic of cash moving toward the designatedsection of the screen). Money is just one example; other types ofinformation that may be sent include virtual currency amounts, wagers,images, videos, text messages, etc. to name a few examples.

In an embodiment, the transfer between mobile communications device 102b and mobile communications device 102 a may occur without further inputfrom the user of the mobile communications device 102 b (the originatorof the transfer of information). This may occur, for example, where theuser of the mobile communications device 102 b has previously identifiedthe mobile communications device 102 a as a trusted recipient, themobile communications device 102 b has automatically identified themobile communications device 102 a as a trusted recipient based on aprevious similar action, or based on the value of the transfer beingless than a threshold amount (whether set by default or the user ofeither the mobile communications device 102 b or 102 a). For example,the mobile communications device 102 b may be allowed to transmit moneydirectly to the designated recipient in response to an appropriate swipeto the appropriate section of the display screen if the amount is lessthan (or equal to in some embodiments) $10 (as just one example, anyother value could be selected or set by default as well).

In an alternative embodiment, the transfer may require confirmation bythe user of the mobile communications device 102 b before completing thetransfer to the intended recipient (in this example, mobilecommunications device 102 a), for example for all transfers or fortransfers above a particular value (or, for messages or images, fortransfers to “untrusted” recipients, such as those that have not beenidentified as trusted yet). For example, a confirmation window may bedisplayed on the screen of the mobile communications device 102 brequesting the user to tap a button in the confirmation window toconfirm or deny the transmission and/or together with one or both of anauditory notification (e.g., a chime) and a tactile notification such asvibration (the particular combination may be set by the user or bydefault). The confirmation window (and/or other notification) may besatisfied with a tap on an appropriate button or pre-defined section ofthe screen. Alternatively, the user may be allowed to shake the mobilecommunications device 102 b to confirm transmission (which may bedetected by appropriate hardware at the device such as viaaccelerometer).

Either way, the information may then be transmitted from the mobilecommunications device 102 b to the mobile communications device 102 a(whether via P2P session 104 or uplink 106 b/downlink 106 a). Receipt ofthe information triggers a notification at the mobile communicationsdevice 102 a. This may include a passive notification shown when thescreen is locked at the mobile communications device 102 a, and/or alight notification, or may be configured to display only when the userof the mobile communications device 102 a next logs in beyond the lockedscreen. The notification may request the user of the mobilecommunications device 102 a to accept or reject the information receivedfrom the mobile communications device 102 b, here the monetary amount inthis example. Alternatively, the mobile communications devices 102 insuch a group may be configured to automatically accept informationreceived from each other via the group. Upon acceptance or rejection,the mobile communications device 102 a may then transmit a statusresponse to the sender mobile communications device 102 b identifyingthe acceptance or rejection.

One exemplary embodiment of the mobile communications devices 102 isdepicted in FIG. 2. In FIG. 2, the mobile communication devices 102include a transceiver 202, a memory 204, a processor 206, a userinterface 208, a data store 210, a location determination system 212, aposition sensor 214, and a swipe interpretation system 216. Theseelements may be in direct or indirect communication with each other, forexample via one or more buses.

The transceiver 202 may include a modem subsystem and a radio frequency(RF) unit and be configured to communicate bi-directionally with otherdevices, such as other mobile communications devices 102 and/or thenetwork 108. The memory 204 may include a cache memory (e.g., a cachememory of the processor 206), random access memory (RAM),magnetoresistive RAM (MRAM), read-only memory (ROM), programmableread-only memory (PROM), erasable programmable read only memory (EPROM),electrically erasable programmable read only memory (EEPROM), flashmemory, solid state memory device, hard disk drives, other forms ofvolatile and non-volatile memory, or a combination of different types ofmemory. In an embodiment, the memory 204 includes a non-transitorycomputer-readable medium.

The memory 204 may store instructions that, when executed by theprocessor 206, cause the processor 206 to perform the operationsdescribed herein in connection with embodiments of the presentdisclosure. Instructions may also be referred to as code. The terms“instructions” and “code” may include any type of computer-readablestatement(s). For example, the terms “instructions” and “code” may referto one or more programs, routines, sub-routines, functions, procedures,etc. “Instructions” and “code” may include a single computer-readablestatement or many computer-readable statements.

The processor 206 may include a central processing unit (CPU), a digitalsignal processor (DSP), an application-specific integrated circuit(ASIC), a controller, a field programmable gate array (FPGA) device,another hardware device, a firmware device, or any combination thereofconfigured to perform the operations described herein and discussed inmore detail below. The processor 206 may also be implemented as acombination of computing devices, e.g., a combination of a DSP and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration. The processor 206 may be a single processor or multipleprocessors, where each processor may have one or more processing corescapable of parallel and/or sequential operation.

The user interface 208 may include an input component and an outputcomponent. For example, the user interface 208 may include a touchscreeninterface that outputs data for visual use as well as receives/processesone or more touches/swipes/gestures to be potentially interpretedaccording to embodiments of the present disclosure such as discussedwith respect to swipe interpretation system 216. Further, the userinterface 208 may be used to display one or more notifications, elementsof information, and application data according to embodiments of thepresent disclosure. The user interface 208 may also include one or morelights (e.g., LEDs) separate from a touchscreen, a vibration generator,a speaker, a microphone, input for a mouse, input for a keyboard, etc.useful for providing feedback to a user as well as receiving furtherinput therefrom.

The data store 210 may be, for example, a hard drive, flash drive,storage array, or other type of storage. The data store 210 may storenotifications, transferred information, location information, mapinformation, and/or update information (e.g., as an “app”).

In an embodiment, the location determination system 212 may include oneor more transceivers to enable communication with the GNSS 110illustrated in FIG. 1. The mobile communications devices 102 a/102 b/102c may further include assisted-GPS for enhanced signalacquisition/location quality.

The position sensor 214 may be an orientation and/or motion detectioncomponent, such as a gyroscope and/or accelerometer. It may be used incombination with gesture detection according to embodiments of thepresent disclosure, such as for confirmation to send information toanother device or to accept receipt of information from another device.

The swipe interpretation system 216 may be an example of the appmentioned above with respect to the data store 210. In an embodiment,the swipe interpretation system 216 is an application that communicateswith the other components of the mobile communications device 102. Forexample, the swipe interpretation system 216 assists in prompting a userof the mobile communications device 102 in storing assignments ofsections of the touchscreen of the user interface 208 to differententities, such as different mobile communications devices 102 in thesame group. This may include prompts to the user on the touchscreen,upon activation of the “app,” on how to assign different sections of thetouchscreen to different entities while the “app” is being accessed.

The swipe interpretation system 216 also monitors output from the userinterface 208, for example identifying a swipe on the user interface 208where it is a touchscreen. According to embodiments of the presentdisclosure, various sections of the screen of the user interface 208 mayhave been previously assigned to different entities that have joined thesame group. When the mobile communications device 102 detects a swipe onthe touchscreen 208, for example under the control of the processor 206,information about the detected swipe is transferred to the swipeinterpretation system 216. This information may include various touchparameters, at least including the location of all (or at least asufficiently large sampling) touch points on the touchscreen of theswipe (for example as a function of time, so that the first and lasttouch points are identifiable to assist in finding the direction of theswipe).

With this information, the swipe interpretation system 216 determinesthe direction in which the detected swipe was directed. This may includedetermining, from the set of touch points received, a vector of theswipe. As another example, the swipe interpretation system 216 may fit acurve to the set of touch points and determine a direction of the swipefrom the fitted curve. Either way, the swipe interpretation system 216may compare the determined direction of the swipe with the location, onthe touchscreen, of the different assigned sections (assigned to thedifferent entities in the group). The swipe interpretation system 216may estimate a further track of the detected swipe based on thedetermined direction of the swipe to determine whether it would haveintercepted any point of any of the sections of the touchscreen. Asanother example, the swipe may end over some assigned section, in whichcase the swipe interpretation system 216 determines that the swipephysically ended on a point of an assigned section of the touchscreen.

In an embodiment, the swipe interpretation system 216 determines thatthe detected swipe was directed towards an assigned section if thedetermined direction would intercept some point of an assigned section.In an alternative embodiment, the swipe interpretation system 216 mayinclude a threshold region surrounding the assigned sections on thetouchscreen where, if the determined direction intercepts a point in thethreshold region but not the assigned section itself, it determines thatthe detected swipe was directed towards the assigned section. In thiscase, the swipe interpretation 216 may dynamically adjust the size ofthis threshold region as a function of the number of assigned sectionscorresponding to the number of entities (e.g., other mobilecommunications devices 102) in the group at any given time.

Thus, if there are a small number of entities in the group, andtherefore a correspondingly small number of assigned sections on thetouchscreen of the user interface 208, the threshold region may be havea moderately large value so that less accurate swipes may still resultin a positive identification of a swipe to an assigned section. Further,if there are a relatively large number of entities in the group, andtherefore a correspondingly large number of assigned sections, the swipeinterpretation system 216 may dynamically decrease the value for thethreshold region, sometimes removing it completely when there are manyentities in the group, so that positive identifications are reduced tosituations that are closer to, actually do, intercept a point in anassigned section.

To avoid misinterpreting the meaning or intent of a swipe on thetouchscreen of the user interface 208, the swipe interpretation system216 may ignore swipes while the “app” is not activated by the userand/or running in the background. Thus, the system may wait until theuser activates the swipe interpretation functionality in a multi-peersetting to implement embodiments of the present disclosure.

When the swipe interpretation system 216 determines that a swipe wasdirected toward an assigned section of the touchscreen of the userinterface 208, it directs the transceiver 202 to initiate transmissionof information relevant to the purpose of the “app”—for example, amonetary amount, a message, an image, a wager, etc. In embodiments whereno confirmation is required (whether for any transmission based on aswipe determination, or based on the swipe interpretation system 216further determining that a value in the information to be sent fallsbelow a threshold for the value), the transceiver 202 completestransmission of the information without requiring further input from theuser of the mobile communications device 102. In alternative embodimentswhere confirmation is required (whether by default or because the swipeinterpretation system 216 determines that the value falls at or abovethe threshold, for example), the swipe interpretation system 216 maydirect the mobile communications device 102 request a confirmation fromthe user before completing transmission.

For example, the swipe interpretation system 216 may direct some aspectof the user interface 208 to alert the user to provide confirmation.This may assume the form of a chime output from a speaker, a lightflashing from an LED, a vibration, or some combination of these thingsthat may direct the user of the mobile communications device 102 tointeract with a confirmation window generated on the touchscreen of theuser interface 208. The confirmation window may include a button toconfirm and a button to deny that the transmission should be sent to theidentified recipient. In an alternative embodiment, the swipeinterpretation system 216 may direct the transceiver 202 to transmit amessage to a smartwatch that the mobile communications device is pairedwith (in embodiments where this is the case) to request confirmation atthe smartwatch to complete the transmission to the identified recipient.Confirmation may additionally or alternatively come in the form of adetected level of shaking or voice input, to name some examples.

If confirmation is received (whether from a confirmation window on thetouchscreen of the user interface 208 or from a smartwatch thattransmits the results of a confirmation there to the transceiver 202 forthe swipe interpretation system 216 to cause the information to be sentto the identified recipient), then the swipe determination system 216directs the transceiver to complete transmission of the information.

In embodiments where the mobile communications device 102 is part of agroup and another entity in the group has selected to transmitinformation to the mobile communications device 102, the swipeinterpretation system 216 of the receiving mobile communications device102 may assist with notification and confirmation. For example, theswipe interpretation system 216 may be triggered, upon the transceiver202 receiving the information, to cause one or more components of theuser interface 208 to output a notification. This may include a passivenotification when the touchscreen of the user interface 208 is locked.This may further or alternatively include a light notification (e.g.,activation of one or more LEDs). The swipe interpretation system 216 mayfurther cause the touchscreen to display a notification when the usernext logs in. The notification may request the user of the mobilecommunications device 102 to accept or reject the information receivedfrom the entity. Alternatively, the swipe interpretation system 216 maydirect the mobile communications device 102 to automatically accept theinformation. Upon acceptance or rejection, the swipe interpretationsystem 216 may then direct the transceiver 202 to transmit a statusresponse to the sending entity with the result.

Turning now to FIG. 3, a block diagram is illustrated of an exemplarymobile communications device 102 according to embodiments of the presentdisclosure. For simplicity of discussion, reference will be made tomobile communications device 102 b from FIG. 1 above, where as discussedwith respect to the example in FIG. 1 the mobile communications device102 b is in communication with two other entities in a group, mobilecommunications devices 102 a and 102 c. This is for simplicity ofdiscussion only. Other numbers of entities may also be included in thegroup.

The mobile communications device 102 b may have the components describedwith respect to FIG. 2 above. FIG. 3 illustrates the touchscreen of theuser interface 208, referred to here for simplicity as the touchscreen208. As can be seen in FIG. 1, the mobile communications device 102 a isabove and to the left of the mobile communications device 102 b. In FIG.3, the mobile communications device 102 a has been associated (e.g., bythe swipe interpretation system 216 of the mobile communications device102 b) with the section 302 a in the upper left corner of thetouchscreen 208. As further seen in FIG. 1, the mobile communicationsdevice 102 c is above and to the right of the mobile communicationsdevice 102 b. In FIG. 3, the mobile communications device 102 c has beenassociated (e.g., by the swipe interpretation system 216) with thesection 302 c in the upper right corner of the touchscreen 208.

In an embodiment, the swipe interpretation system 216 may assign thesections 302 a and 302 c as static section assignments on thetouchscreen 208. Thus, though any one (or more) of the mobilecommunications devices 102 a/102 b/102 c may move over a time periodthat embodiments of the present disclosure are active on the touchscreen208, the assigned sections may remain in the same assigned corners.

In an alternative embodiment, the assigned sections 302 a and 302 c maybe dynamic. Thus, as any one (or more) of the mobile communicationsdevices 102 a/102 b/102 c move over time, the assigned sections may moveas well to reflect a general correspondence between where the devicesstand in relation to each other geographically. For example, the mobilecommunications device 102 b may determine its own location based oninformation obtained from the location determination system 212discussed above with respect to FIG. 2. Similarly, the other devices inthe group (mobile communications devices 102 a/102 c) may periodicallysend updated location information to each other (and mobilecommunications device 102 b to the others). The swipe determinationsystem 216 may use this information to update where on the touchscreenthe associated sections are found.

As illustrated in FIG. 3, the position of the mobile communicationsdevice 102 c may change over time relative to the position of the mobilecommunications device 102 b. The swipe determination system 216determines this based on updated location information for the variousdevices, and updates the position of the section 302 c to shift 306 tolocation 304 on the touchscreen 208. The shift may be visible as amovement from the current location to the new location 304 (e.g., inreal time or near-real time), or may be removed from its currentlocation and reproduced at the new location 304.

As illustrated in FIG. 3, each section 302 a, 302 c is blank. In anembodiment, assigned sections may be fully opaque so that no underlyingimage/information is visible. In another embodiment, the assignedsections may be partially transparent, so that a user viewing thetouchscreen 208 may recognize the extent of the assigned sections 302 a,302 c while still be able to discern the information underlying theassigned sections 302 a, 302 c. In addition or in the alternative, eachassigned section 302 a, 302 c may include one or more identifiers forthe mobile communications devices 102 a, 102 c to which the assignedsections correspond. For example, assigned section 302 a may have aname, number, image, or some combination of the above displayedsomewhere in the assigned section 302 a that identifies the mobilecommunications device 102 a (and/or the user of the mobilecommunications device 102 a) and likewise with respect to assignedsection 302 c for mobile communications device 102 c. The identifier maybe generated by the mobile communications device 102, or may be receivedfrom the other peer devices in the group.

In an embodiment, one or more mobile communications devices 102 that arewithin the group that mobile communications device 102 b is in may serveas relays to other mobile communications devices 102. This may occur,described here in the context of the example of FIG. 1, where there isanother mobile communications device 102 that is within range of mobilecommunications device 102 c but not the mobile communications devices102 a or 102 b. This may occur at joining, or over time as a device mayleave the range of one or more of the mobile communications devices 102a/102 b/102 c but still seek to remain in the group to participate(e.g., where the devices are connected via some P2P mechanism such as aD2D connection).

The mobile communications device 102 that is out of range to mobilecommunications device 102 b, but within range of mobile communicationsdevice 102 c (whether joining while out of range or moving out of rangeafter joining the group), may retain its own assigned section on thetouchscreen 208. When a swipe is directed to that out-of-range mobilecommunications device 102 (to the assigned section), the use of themobile communications device 102 c as a relay to that device may be donetransparently to the user of the mobile communications device 102 b.Alternatively, when a mobile communications device 102 moves out ofrange of one or more of the mobile communications device 102 b, theassigned section on the touchscreen 208 may merge into the assignedsection for the device that functions as relay, in this example mobilecommunications device 102 c. As part of this merging, the assignedsection 302 c may add additional information about the relay option onreaching the out-of-range device, or may split the section in half, onehalf for the mobile communications device 102 c and the other for theout-of-range device, to name just a few examples.

Looking at a particular example in FIG. 3, a swipe 308 is detected onthe touchscreen 208. As illustrated, the lower left portion of the swipe308 is the beginning of the swipe 308, with the direction of the swipe308 progressing upward and to the right across the touchscreen 208 overa period of time. The data corresponding to the swipe 308 is received,processed, and conveyed to the swipe interpretation system 216 forexample as discussed above with respect to FIG. 2.

The swipe interpretation system 216 determines whether the swipe 308 isdirected towards an assigned section of the touchscreen 208, for exampleby determining whether the swipe 308, had it progressed from the pointit ended, would have intercepted any point of any of the sections of thetouchscreen 208 (or, where the swipe ends on a point of an assignedsection, which section that ending point occurred at). In an embodiment,when the swipe 308 does not end in any assigned section, the swipeinterpretation system 216 may determine whether the swipe 308 would haveprogressed to a threshold region around an assigned section.

In the example of FIG. 3, the swipe interpretation system 216 maydetermine that the swipe 308 would have intersected the assigned section302 c (had it continued on its present direction) which corresponds tomobile communications device 102 c. In the example illustrated in FIG.3, before the swipe occurred the user set the information that itdesired to transmit to another peer device, here an amount of money.Then the swipe interpretation system 216 informed the user via thetouchscreen 208 that it was ready to receive a swipe to indicate whichmobile communications device to send the money to. With the swipe 308detected and interpreted, the swipe interpretation system 216 causes themobile communications device 102 b to proceed with transmitting thedesignated amount (as the particular example of information here).

In an embodiment, the swipe interpretation system 216 may cause thetransmission to proceed without further confirmation, thereby providingan easy and convenient way to transmit information in a multi-peercontext. In an alternative embodiment, the swipe interpretation system216 may first require confirmation via either the touchscreen 208 orsome paired device associated with the user of the mobile communicationsdevice 102 b, such as a smartwatch. After the information has beentransmitted to the mobile communications device 102 c, here the monetaryamount, the mobile communications device 102 b may receive aconfirmation of acceptance (or rejection) of the transmitted informationafter a period of time. The confirmation may be sent to the mobilecommunications device 102 b, to a paired device, or to both to name someexamples.

A few example use scenarios will now be discussed in order todemonstrate a few aspects of embodiments of the present disclosure. Forexample, FIG. 4 is a diagram of an exemplary wireless communicationsenvironment 400 for online gaming according to embodiments of thepresent disclosure. Similar to the environment 100 of FIG. 1, theenvironment 400 includes mobile communications devices 102 a, 102 b, and102 c and GNSS 110. The mobile communications devices 102 a, 102 b, and102 c are connected to each other via P2P sessions 104 (e.g., D2Dlinks). The wireless communications environment 400 further includes acommon pool 402 that the mobile communications devices 102 a, 102 b, and102 c are connected with via connections 404 a, 404 b, and 404 c,respectively. The connections 404 a, 404 b, and 404 c may be directlinks, e.g., D2D links, or alternatively via connections to a network,such as network 108 illustrated in FIG. 1.

In the illustrated embodiment of FIG. 4, an identifier is provided witheach assigned section 406 b, 406 c, and 406 d on the touchscreen of themobile communications device 102 a (exemplary of the other mobilecommunications devices). In an embodiment, the mobile communicationsdevice 102 a may communicate with the GNSS 110 to at least periodicallyupdate location information. The mobile communications device 102 a mayadditionally communicate with the other mobile communications devices102 b/102 c to send and receive updated location information for thosedevices. Where the common pool 402 is hosted by a server, the locationmay be provided via GNSS information and/or location based on IP address(just to name a few examples). The assigned sections 406 b, 406 c, and406 d may dynamically move about the periphery of the touchscreen of themobile communications device 102 a as discussed above with respect toFIG. 3, based on the orientation of the mobile communications device 102a at any given point in time.

The common pool 402 may be maintained at a server that is independentfrom the mobile communications devices 102 a/102 b/102 c. The commonpool 402 may be, for example, a common pool to which each of the mobilecommunications devices 102 a/102 b/102 c may periodically sendinformation (e.g. monetary value) and receive information. In theexample of FIG. 4, the common pool 402 may be a hosted pot for money orsome other form of real or virtual currency.

In this example, each of the mobile communications devices 102 a/102b/102 c may have occasion to desire to transmit information to thecommon pool 402. For example, the mobile communications devices 102a/102 b/102 c may be connected to each other for the purposes of anonline game, such as a poker game. Therefore, when a bid or ante is tobe put into the “pot,” the user of a given mobile communications device102 a (as just one example representative of the other devices as well)may swipe on their touchscreen toward the section 406 d on theirtouchscreen associated with the common pool 402. In an embodiment, theuser may use different combinations of gestures to signal differentamounts to transfer. For example, a single finger swipe detected may bedetermined to correspond to a first fixed amount (e.g., fixed by defaultor by the user previously), a two-finger swipe detected may bedetermined to correspond to a second fixed amount (e.g., greater thanthe first and fixed by default or the user previously), etc.

In response, the mobile communications device 102 a transmitsinformation identifying an amount to be put into the pot via theconnection 404 a. The touchscreen of the mobile communications device102 a may display pool and personal amounts 408 to update the user oftheir current status. In an embodiment, the transmission may occurwithout any confirmation. In another embodiment, the mobilecommunications device 102 a may first seek confirmation from the user ofthe device that the amount is desired to be sent, which may for examplebe performed by a touch to a relevant portion of the screen or byshaking the device.

In an embodiment, the server hosting the common pool 402 may maintain arunning total of the amount in the pool contributed from one or more ofthe mobile communications devices 102 a/102 b/102 c, and send updates toeach of the mobile communications devices 102 a/102 b/102 c when changesto the pool amount occurs. In an alternative embodiment, the common pool402 may not be hosted by a server but instead be a virtualrepresentation of a pool, such that when the user of the mobilecommunications device 102 a swipes towards the section 406 d tocontribute to the common pool 402, the mobile communications device 102a may in actuality send the information directly to the other mobilecommunications devices 102 b/102 c as an update for the pool amount 408maintained at each of those devices.

Although illustrated in FIG. 4 as being located separately from themobile communications devices 102 a/102 b/102 c, the common pool 402 mayalternatively be hosted by one of the mobile communications devices 102a/102 b/102 c. For example, if the mobile communications device 102 bwere to host the common pool 402, the other mobile communicationsdevices 102 a/102 c may detect swipes directed towards the mobilecommunications device 102 b and, due to the specific context for thesedevices, determine that they are intended toward the common pool 402hosted by the mobile communications device 102 b.

Alternatively, each of the mobile communications devices 102 a/102 c mayassign multiple sections with respect to the mobile communicationsdevice 102 b, such as a section specifically for the hosted common pool402 and a separate section specifically for the mobile communicationsdevice 102 b. These sections may be proximate to each other, reflectingthe general relative location of the mobile communications device 102 bto the mobile communications devices 102 a/102 c.

Another example use scenario is illustrated in FIG. 5, which provides adiagram of an exemplary wireless communications environment 500 in aretail scenario (e.g., in a restaurant) according to embodiments of thepresent disclosure. The environment 500 may include the mobilecommunications devices 102, GNSS 110, and network 108, as well as mobiledevices W1, W2, W3, W4, and W5.

The mobile devices W1, W2, W3, W4, and W5 are representative of mobiledevices associated with different wait staff in the wirelesscommunications environment of FIG. 5. These may be, for example, mobilecommunications devices such as cellular phones (e.g., whether providedby the establishment or the wait staff's own personal devices). Asanother example, each of mobile devices W1, W2, W3, W4, and W5 may be anRFID tag. Some combination of the above may also occur. The mobiledevices W1, W2, W3, W4, and W5 may be in communication with one or moreother devices.

In the illustrated embodiment of FIG. 5, the mobile communicationsdevice 102 b rests on a table (or held in the hands of a user of thedevice at the table) in the restaurant. In an embodiment, the mobilecommunications device 102 b may connect with the mobile devices W1 andW2 via direct links 514.1 and 514.2, respectively (e.g., D2D links orBluetooth links). Alternatively, the mobile communications device 102 bmay connect with the mobile devices W1 and W2 via a network 108, whichmay represent a Wi-Fi network at the restaurant as one example. Thus,the mobile communications device 102 b may establish connection 106 bwith the network 108, which in turn has connections 512.1 and 512.2 withthe mobile devices W1 and W2, respectively.

In the illustrated embodiment of FIG. 5, a radius 516 may be imposedarbitrarily or due to physical limitations (e.g., communication rangelimitation of the particular technology used to connect). For example,to reduce the complexity and number of assigned sections appearing onthe touchscreen of the mobile communications device 102 b, a defaultradius 516 may be set so that any mobile devices W beyond that radiusare not included for display on the touchscreen. The radius 516 mayalternatively be set by the user at some previous time or at the time ofthe visit to the restaurant (and dynamically changed during the visit).Based on the illustrated radius 516 in FIG. 5, the touchscreen on themobile communications device 102 b has sections assigned for the mobiledevices W1 and W2, which fall within the radius 516, but not the mobiledevices W3, W4, and W5.

When the user of the mobile communications device 102 b desires totransmit information to wait staff associated with the mobile devicesW1, W2 that are within the radius 516, the user swipes towards theappropriate section on the touchscreen (whether a static section ordynamic section as discussed with respect to FIG. 3 above). In anembodiment, any number of touch points (e.g., from any number offingers, stylus, etc.) may result in the same determination, such as totransmit the information set previously by the user on the touchscreenof the mobile communications device 102 b. In an alternative embodiment,the number of touch points (fingers, stylus, etc.) may correspond todifferent predetermined types of information to be sent.

For example, a single finger swipe may result in transmitting a firsttip value, a double finger swipe may result in a second tip value, e.g.,greater than the first, etc. As another example, a single finger swipemay result in transmitting information pre-set on the touchscreen (e.g.,typed in or selected at a time prior to the swipe), a double fingerswipe may result in transmission of a pre-set tip amount, etc. Asanother example, swipes to two different sections may be madesubstantially simultaneously, which the mobile communications device 102b may interpret by sending the same information to both identifiedrecipients. As another example, the speed of one or more swipes may beused to determine either the specific information to be sent, and/or theintended recipient

In some embodiments, the environment 500 may be used to allow the userof the mobile communications device 102 b to transmit tip amounts towait staff as desired. In other embodiments, the information sent by aswipe may include an order or a change to an existing order. Forexample, where the swipe results in transmitting a change to an order,the mobile communications device 102 b may receive a confirmation of theoriginal order, e.g. as taken by wait staff, and be allowed to changethe order while it is being prepared by transmitting a change to waitstaff within the radius 516. As another example, the swipe to a waitstaff (here, W1 or W2) may result in transmitting information previouslyset on the screen (e.g., whether typed by the user or selected by theuser), such as to indicate a request for assistance or to provide otherfeedback.

In an embodiment, a central server managed by the restaurant may trackthe information sent to the wait staff over time, for example to examinedifferent performance metrics of the wait staff, business analytics todetermine how people are using the system, what information is mostuseful in the system, what information is least useful, etc. Where themobile communications device 102 b communicates with the mobile devicesW via the network 108, the information may be split between the mobiledevices W and the central server. Alternatively, the mobile devices Wmay forward this information on to the central server (whether there areD2D links to the mobile communications device 102 b or connections viathe network 108).

As another example within the environment 500 of FIG. 5, embodiments ofthe present disclosure may be utilized to assist multiple parties tosplit a bill amongst themselves. For example, where multiple mobilecommunications devices 102 are joined in the same group, for examplecorresponding to users at the same table or tables at a restaurant, thegroup may use these features to assist in splitting a bill. The bill maybe received in paper form, with the value entered in manually to one ormore of the mobile communications devices 102 in the group, or may beemailed by the restaurant. Each user of each mobile communicationsdevice 102 may swipe to an assigned section of their respectivetouchscreen, for example a common pool like that discussed in FIG. 4, totransfer a specified portion of the bill from their account to either ahosting mobile communications device 102 in the group to pay the entirebill, or to pay the entire bill in aggregate from each of the devices inthe group. Where the individual contributes do not amount to the totalbill, this information may be spread through the group to request anadditional contribution, for example displayed together with the totalcontributions so far from each member of the group (for example overlaidon their respective assigned sections on the touchscreen), and also forexample with a proposed percentage split for each device in the groupcalculated to complete the bill.

Another example use scenario is illustrated in FIG. 6, which provides adiagram of an exemplary wireless communications environment 600 in apaired device scenario according to embodiments of the presentdisclosure. The environment 600 may include the mobile communicationsdevices 102 a/102 b/102 c, GNSS 110, network 108, and paired device 612.The paired device 612 is illustrated in FIG. 6 as being a smartwatch;this is exemplary only. The paired device could be any number of devicesthat are capable of pairing with the mobile communications device 102 b(as an example), such as via Bluetooth, D2D, NFC, etc. The elements inFIG. 6 that are similarly numbered to those in FIG. 1 will not bediscussed in detail here, relying instead on the discussion above withrespect to FIG. 1.

In the example environment 600 of FIG. 6, when the mobile communicationsdevice 102 b is ready to transmit information (e.g., a swipe toward anassigned section of the touchscreen has been detected and processed),the mobile communications device 102 b (for example, under the directionof the swipe interpretation system 216 described in FIG. 2) transmits aconfirmation request to the paired device 612. In an embodiment, theconfirmation request includes display information 614 for the paireddevice 612 to display in furtherance of the confirmation. Alternatively,the paired device 612 may already have various confirmation alternativesstored locally, which the confirmation request triggers the paireddevice 612 to access (or directs which to select).

Upon receiving the confirmation request, the paired device 612 displaysthe display information 614. In an embodiment, the paired device 612 maybe a device owned and/or operated by the same user associated with themobile communications device 614. This may provide an added layer ofsecurity, for example where sensitive information or monetary amountsare sought to be transferred by a swipe according to embodiments of thepresent disclosure. In another embodiment, the paired device 612 may beassociated with a different user than the user of the mobilecommunications device 102 b that seeks to transmit the information. Forexample, the paired device 612 may be operated by a parent of a childwho operates the mobile communications device 102 b, thereby allowingparental supervision of transfers of such things as monetary value, etc.

After presenting the display information 614 to the user of the paireddevice 612, the paired device 612 may wait for an input in response. Inan embodiment, the paired device 612 may wait a predetermined amount oftime, after which if no input has been received the display information614 may be updated (e.g., with an additional notification alert such asa sound or vibration in the paired device 612) or the confirmation timedout. If the confirmation request times out due to a lack of user input,the paired device 612 may transmit a notification of this back to themobile communications device 102 b. In response, the mobilecommunications device 102 b may have the option to send anotherconfirmation request to the paired device 612, seek confirmation via themobile communications device 102 b's own touchscreen, or proceed withtransmitting the information without confirmation (or have an optionpre-selected as the default action to take in this situation).

Where the user does provide the appropriate input response to thedisplay information 614, the paired device 612 may transmit theconfirmation back to the mobile communications device 102 b. Theconfirmation request may have specified a particular type of inputresponse that will be recognized as confirmation (e.g. a specific numberof distinct taps). Alternatively, the paired device 612 may be left toits own determination of what type of input qualifies as an appropriateinput response to the display information 614. Some examples of inputincludes one or more taps on the screen of the paired device 612, ageneric swipe on the screen, a swipe to a specified section of thescreen, voice input (e.g., voice recognition of “yes” or “no”), etc.

Once the user of the paired device 612 confirms that the transmissionshould occur (e.g., either by simply approving or approving where thereis also an option to deny), the confirmation is transmitted back to themobile communications device 102 b, which proceeds with transmitting theinformation.

Turning now to FIG. 7, a flow diagram illustrates a method 700 forenhanced peer-to-peer networking exchanges according to an embodiment ofthe present disclosure. The method 700 will be described with respect toa mobile communications device 102 for simplicity of discussion, thoughit will be recognized that the aspects described herein may beapplicable to a plurality of mobile communications devices 102. It isunderstood that additional steps can be provided before, during, andafter the steps of method 700, and that some of the steps described canbe replaced or eliminated for other embodiments of the method 700.

At block 702, the mobile communications device 102 establishes P2Pcommunications with one or more other mobile communications devices 102(referred to here as peer devices), for example according to one or moreof the ways described above with respect to FIG. 1. For example, themobile communications device 102 may establish all of the different P2Pcommunications using the same technology and protocol, or may establishdifferent communications with different technologies/protocols.

At block 704, the mobile communications device 102 assigns a section ofthe touchscreen to a peer device. In an embodiment, the assignment maybe according to a default order, for example the upper left corner isassigned first, then the upper right, then the lower right, then thelower left depending upon the number peer devices. In anotherembodiment, the assignment may be according to a relative location ofthe mobile communications device 102 to the connected peer device, suchas made possible by information from the GNSS 110.

At decision block 706, the mobile communications device 102 determineswhether there are additional peer devices to which the mobilecommunications device 102 is in communication that need a section of thetouchscreen assigned. If so, then the method 700 turns to the next peerdevice at block 708 and returns to block 704 to continue as discussedabove.

If there are no more peer devices that have not yet been assigned asection of the touchscreen, then the method 700 proceeds to block 710.

At block 710, the mobile communications device 102 receives locationinformation of one or more of the peer devices. For example, the peerdevices may broadcast their location information periodically to one ormore of the other peer devices that they are connected to.

At block 712, the mobile communications device 102 determines its ownlocation information, for example via communication with GNSS 110 ofFIG. 1 or by some other means, such as triangulation to nearby basestations, etc. The actions at blocks 710 and 712 may be interchangeableor occur substantially simultaneously.

At decision block 714, the mobile communications device 102 determineswhether there have been any relative changes between the mobilecommunications device 102 and any of the paired devices. In making thisdetermination, the mobile communications device 102 uses the locationinformation received at block 710 and determined at block 712. Forexample, the mobile communications device 102 may compare the locationinformation of the mobile communications device 102 against a previouslocation recorded for the mobile communications device 102 to identifyany change, and/or location information of the peer devices againstpreviously stored location information for those devices, and/orlocation information of the mobile communications device 102 against thelocation information of the peer devices.

In an embodiment, the mobile communications device 102, when determiningrelative change, may further determine whether any detected relativechange between devices exceeds a defined threshold, so that the assignedsections remain relatively stationary until sufficiently large changeswarrant an update on the location of the sections. For example, amovement of a few degrees in relative change may not rise above thedefined threshold, so that small movements do not cause unnecessaryactivity on the screen.

If it is determined at decision block 714 that a relative change hasoccurred, then the method 700 proceeds to block 716. At block 716, themobile communications device 102 updates the section assignment(s) ofthe peer device(s) whose locations have changed relative to the mobilecommunications device 102.

If it is instead determined at decision block 714 that no relativechange has occurred, or in embodiments where there is the determinedthreshold, that the relative change does not exceed the determinedthreshold, then the method 700 proceeds to block 718.

In embodiments where the sections of the touchscreen are staticallyassigned (e.g., relative movement does not influence the locations ofthe sections on the touchscreen), the actions at blocks 710 to 716 maybe skipped.

At block 718, a gesture on the touchscreen of the mobile communicationsdevice 102 is detected. For example, the mobile communications device102 may detect a swipe type of gesture on the touchscreen (e.g., of oneor more fingers). Although illustrated in FIG. 7 as directly followingthe relative change detection, the detection at block 718 may occurprior to or concurrent with the relevant change detection occurring atblocks 710-716.

At decision block 720, the mobile communications device 102 determineswhether the detected gesture from block 718 was directed towards anassigned section of the touchscreen, for example as described above withrespect to FIG. 3. If not, then the method returns to block 710.

If the mobile communications device 102 instead determines that thedetected gesture was directed toward an assigned section, and whichspecific device the gesture was directed towards, the method 700proceeds to block 722.

At block 722, the mobile communications device 102 determines the numberof gestures detected from block 718. For example, multiple gesturestowards the same (or different) sections may indicate different types,or amounts, of information that is desired to be transmitted to theassociated recipient peer device(s). This may be an optional block inthe method 700, for example where multi-gesture detection is notsupported or desired.

At block 724, the mobile communications device 102 initiates a transferof the desired information to the identified recipient(s) from blocks720 and 722 (where applicable).

At decision block 726, if a confirmation is required by a user, such asthe user of the mobile communications device 102, then the method 700proceeds to block 728.

At block 728, the mobile communications device 102 requestsconfirmation. For example, this may include displaying a confirmationrequest on the touchscreen of the mobile communications device 102. Asanother example, this may include transmitting a confirmation request toa paired device, such as described above with respect to the example inFIG. 6, and waiting for a response.

If a confirmation is received, then the method 700 proceeds from block728 to block 730. If confirmation is not received, or declined, then themethod 700 may return to block 724 to attempt initiation again or mayabandon the transmission attempt.

Returning to decision block 726, if confirmation is not required thenthe method 700 may proceed directly to block 730.

At block 730, the mobile communications device 102 transmits the desiredinformation to the identified recipient(s) from among the peer devicesin the common group. Some examples of desired information may include anamount of money, an amount of virtual currency, wagers, tips, orders,images, videos, text messages, etc.

Turning now to FIG. 8, a flow diagram illustrates an embodiment of amethod 800 for enhanced peer-to-peer networking exchanges according toan embodiment of the present disclosure. The method 800 will bedescribed with respect to a mobile communications device 102 forsimplicity of discussion, though it will be recognized that the aspectsdescribed herein may be applicable to a plurality of mobilecommunications devices 102. It is understood that additional steps canbe provided before, during, and after the steps of method 800, and thatsome of the steps described can be replaced or eliminated for otherembodiments of the method 800.

At block 802, the mobile communications device 102 establishes P2Pcommunications with one or more other peer devices such as discussedabove with respect to block 702.

At blocks 804-808, the mobile communications device 102 assigns asection of the touchscreen to all associated peer device, for example asdiscussed above with respect to blocks 704-708.

At block 810, the mobile communications device 102 receives locationinformation of one or more of the peer devices, for example as discussedabove with respect to block 710.

At block 812, the mobile communications device 102 determines its ownlocation information, for example as discussed above with respect toblock 712.

At block 814, the mobile communications device 102 receives a transferof desired information from at least one of the peer devices (forexample, as transmitted according to blocks 724-730 in FIG. 7).

At block 816, in response to receipt of the information at block 814,the mobile communications device 102 activates a notification on thedevice's display. This may be, for example, a passive notification whenthe touchscreen is locked. This may further or alternatively include alight notification (activation of one or more LEDs) or an auditorynotification (a chime, etc.). This may also include causing thetouchscreen to display a notification when the user next logs in. Thenotification may request the user of the mobile communications device102 to accept or reject the information received from the peer device.

At decision block 818, it is determined whether manual acceptance (e.g.,confirmation) of the received information is required or not. If manualacceptance/confirmation is required, then the method 800 proceeds toblock 820 and performs the confirmation. This may include the userselecting a button identifying acceptance on the touchscreen, or shakingthe mobile communications device 102, etc. Once confirmation isreceived, the method 800 proceeds to block 822. If confirmation is notreceived, or declined, then the mobile communications device 102 maytransmit this result to the peer device that initiated the transmission.

If, at decision block 818, it is determined that manual acceptance isnot required, then the method 800 proceeds to block 822. At block 822,the mobile communications device 102 processes the received information.This may include updating a local account with a value, or opening animage, or text, etc. as the case may be.

Referring now to FIG. 9 an embodiment of a computer system 900 suitablefor implementing, for example, the mobile communications devices, mobiledevices, servers, etc., is illustrated. It should be appreciated thatother devices utilized by users, payment service providers, point ofsale operators, and/or merchants/stores in the system discussed abovemay be implemented as the computer system 900 in a manner as follows.

In accordance with various embodiments of the present disclosure,computer system 900, such as a mobile device, computer and/or a server,includes a bus 902 or other communication mechanism for communicatinginformation, which interconnects subsystems and components, such as aprocessing component 904 (e.g., processor, micro-controller, digitalsignal processor (DSP), etc.), a system memory component 906 (e.g.,RAM), a static storage component 908 (e.g., ROM), a disk drive component910 (e.g., magnetic or optical), a network interface component 912(e.g., modem or Ethernet card), a display component 914 (e.g., CRT orLCD), an input component 918 (e.g., keyboard, keypad, or virtualkeyboard), a cursor control component 920 (e.g., mouse, pointer, ortrackball), a location determination component 922 (e.g., a GlobalPositioning System (GPS) device as illustrated, a cell towertriangulation device, and/or a variety of other location determinationdevices known in the art), and/or a camera component 923. In oneimplementation, the disk drive component 910 may comprise a databasehaving one or more disk drive components.

In accordance with embodiments of the present disclosure, the computersystem 900 performs specific operations by the processor 904 executingone or more sequences of instructions contained in the memory component906, such as described herein with respect to the mobile communicationsdevices, mobile devices, and/or servers. Such instructions may be readinto the system memory component 906 from another computer readablemedium, such as the static storage component 908 or the disk drivecomponent 910. In other embodiments, hard-wired circuitry may be used inplace of or in combination with software instructions to implement thepresent disclosure.

Logic may be encoded in a computer readable medium, which may refer toany medium that participates in providing instructions to the processor904 for execution. Such a medium may take many forms, including but notlimited to, non-volatile media, volatile media, and transmission media.In one embodiment, the computer readable medium is non-transitory. Invarious implementations, non-volatile media includes optical or magneticdisks, such as the disk drive component 910, volatile media includesdynamic memory, such as the system memory component 906, andtransmission media includes coaxial cables, copper wire, and fiberoptics, including wires that comprise the bus 902. In one example,transmission media may take the form of acoustic or light waves, such asthose generated during radio wave and infrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, carrier wave, or anyother medium from which a computer is adapted to read. In oneembodiment, the computer readable media is non-transitory.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by the computer system 900. In various other embodiments ofthe present disclosure, a plurality of the computer systems 900 coupledby a communication link 924 to the network 108 (e.g., such as a LAN,WLAN, PTSN, and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

The computer system 900 may transmit and receive messages, data,information and instructions, including one or more programs (i.e.,application code) through the communication link 924 and the networkinterface component 912. The network interface component 912 may includean antenna, either separate or integrated, to enable transmission andreception via the communication link 924. Received program code may beexecuted by processor 904 as received and/or stored in disk drivecomponent 910 or some other non-volatile storage component forexecution.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the scope of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A mobile device, comprising: a non-transitory memory; and one or more hardware processors coupled to the non-transitory memory and configured to read instructions to cause the system to perform operations comprising: establishing a connection with a first user device and a second user device, wherein the first user device and the second user device are within a threshold distance of the mobile device; assigning a first portion of an interface of the mobile device to the first user device and a second portion of the interface of the mobile device to the second user device, wherein the interface having the first portion, the second portion, and at least a third portion is presented via a visual display component of the mobile device; receiving authentication information for a user of the first user device; determining, based on the authentication information, that the user of the first user device is authenticated at the first user device; detecting an interaction with the first portion of the interface, wherein the interaction comprises a touch gesture with the first portion of the interface; determining that the interaction further comprises a request for a performance of a transaction based on the touch gesture to the first portion of the interface, wherein performance of the transaction requires a payment associated with an account associated with the first user device and the second user device; populating the third portion of the interface of the mobile device with the transaction and the payment associated with the account; and causing the performance of the transaction with the user of the first user device using at least the payment via the account associated with the first user device and the second user device.
 2. The mobile device of claim 1, wherein the causing the performance of the transaction with the user of the first user device includes: requesting a confirmation from a user of the mobile device to approve the transaction if the transaction is at or above a value threshold.
 3. The mobile device of claim 1, wherein the causing the performance of the transaction with the user of the first user device includes: determining if a transaction amount of the transaction is above a threshold transaction amount, and based on determining that the transaction amount of the transaction is above the threshold transaction amount, requesting an additional confirmation from a user of the mobile device to approve the transaction.
 4. The mobile device of claim 1, wherein the detecting the interaction with the first portion of the interface includes detecting a plurality of touch inputs to the first portion of the interface.
 5. The mobile device of claim 4, wherein detecting the plurality of touch inputs further includes determining that the plurality of touch inputs corresponds to a first type of touch interaction, and wherein the first type of touch interaction corresponds to a first transaction amount, and wherein the transaction is performed with the user of the first user device for the first transaction amount.
 6. The mobile device of claim 1, wherein the causing the performance of the transaction with the user of the first user device includes: causing a notification corresponding to the transaction to be displayed on an interface of the first user device, wherein the notification includes a request to accept the transaction.
 7. The mobile device of claim 1, wherein the determining that the user of the first user device is authenticated at the first user device is further based on at least one of if the user of the mobile device has designated the user of the first user device as a trusted user based on trust settings or if the user of the mobile device has performed a transaction with the user of the first user device.
 8. A method comprising: establishing, by a mobile device, a connection with a first user device and a second user device, wherein the first user device and the second user device are within a threshold distance of the mobile device; assigning, by the mobile device, a first portion of an interface of the mobile device to the first user device and a second portion of the interface of the mobile device to the second user device, wherein the interface having the first portion, the second portion, and at least a third portion is presented via a visual display component of the mobile device; receiving authentication information for a user of the first user device; determining, by the mobile device, that the user of the first user device is authenticated at the first user device based on a log in by the user at the first user device using at least the authentication information; detecting an interaction with the first portion of the interface, wherein the interaction comprises a touch gesture with the first portion of the interface; determining, by the mobile device, that the interaction further comprises a request for a performance of a transaction based on the touch gesture to the first portion of the interface, wherein performance of the transaction requires a payment associated with an account associated with the first user device and the second user device; populating the third portion of the interface of the mobile device with the transaction and the payment associated with the account; and causing, by the mobile device, the performance of the transaction with the user of the first user device using at least the payment via the account associated with the first user device and the second user device.
 9. The method of claim 8, wherein the causing the performance of the transaction with the user of the first user device includes: requesting a confirmation from a user of the mobile device to approve the transaction if the transaction is at or above a value threshold.
 10. The method of claim 8, wherein the causing the performance of the transaction with the user of the first user device includes: determining if a transaction amount of the transaction is above a threshold amount, and based on determining that the transaction amount of the transaction is above the threshold transaction amount, requesting an additional confirmation from a user of the mobile device to approve the transaction.
 11. The method of claim 8, wherein the detecting the interaction with the first portion of the interface includes detecting a plurality of touch inputs to the first portion of the interface.
 12. The method of claim 11, wherein detecting the plurality of touch inputs further includes determining that the plurality of touch inputs corresponds to a first type of touch interaction, and wherein the first type of touch interaction corresponds to a first transaction amount, and wherein the transaction is performed with the user of the first user device for the first transaction amount.
 13. The method of claim 8, wherein the causing the performance of the transaction with the user of the first user device includes: causing a notification corresponding to the transaction to be displayed on an interface of the first user device, wherein the notification includes a request to accept the transaction.
 14. The method of claim 8, wherein the determining that the user of the first user device is authenticated at the first user device is further based on if the user of the mobile device has designated the user of the first user device as a trusted user based on trust settings or if the user of the mobile device has performed a transaction with the user of the first user device.
 15. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising: establishing a connection with a first user device and a second user device, wherein the first user device and the second user device are within a threshold distance of a mobile device; assigning a first portion of an interface of the mobile device to the first user device and a second portion of the interface of the mobile device to the second user device, wherein the interface having the first portion, the second portion, and at least a third portion is presented via a visual display component of the mobile device; determining that a user of the first user device is authenticated at the first user device based on at least one of a log in from a locked screen of the first user device or a transaction performed using the first user device and authentication information received at the first user device; detecting an interaction with the first portion of the interface, wherein the interaction comprises a touch gesture with the first portion of the interface; determining that the interaction further comprises a request for a performance of a transaction based on the touch gesture to the first portion of the interface, wherein performance of the transaction requires a payment associated with an account associated with the first user device and the second user device; populating the third portion of the interface of the mobile device with the transaction and the payment associated with the account; and causing the performance of the transaction with the user of the first user device using at least the payment via the account associated with the first user device and the second user device.
 16. The non-transitory machine-readable medium of claim 15, wherein the causing the performance of the transaction with the user of the first user device includes: requesting a confirmation from a user of the mobile device to approve the transaction if the transaction is at or above a value threshold.
 17. The non-transitory machine-readable medium of claim 15, wherein the causing the performance of the transaction with the user of the first user device includes: determining if a transaction amount of the transaction is above a threshold amount, and based on determining that the transaction amount of the transaction is above the threshold transaction amount, requesting an additional confirmation from a user of the mobile device to approve the transaction.
 18. The non-transitory machine-readable medium of claim 15, wherein the detecting the interaction with the first portion of the interface includes detecting a plurality of touch inputs to the first portion of the interface.
 19. The non-transitory machine-readable medium of claim 18, wherein detecting the plurality of touch inputs further includes determining that the plurality of touch inputs corresponds to a first type of touch interaction, and wherein the first type of touch interaction corresponds to a first transaction amount, and wherein the transaction is performed with the user of the first user device for the first transaction amount.
 20. The non-transitory machine-readable medium of claim 15, wherein the causing the performance of the transaction with the user of the first user device includes: causing a notification corresponding to the transaction to be displayed on an interface of the first user device, wherein the notification includes a request to accept the transaction. 